-
Notifications
You must be signed in to change notification settings - Fork 97
clang-tidy.yml: updated to Clang 22 #514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
a51e089 to
a35bc94
Compare
5a14739 to
c4ea47e
Compare
fae2a54 to
2dbb939
Compare
07ed4d7 to
7b28e67
Compare
7ed9517 to
86390b1
Compare
|
LLVM 22.1.0-rc1 has been released so it should be fine to merge this - see https://discourse.llvm.org/t/llvm-22-1-0-rc1-released/89479. |
…-tidy check for now
…` clang-tidy check for now
|
|
||
| bool conditionIsTrue; | ||
| if (ifstates.top() == AlwaysFalse || (ifstates.top() == ElseIsTrue && rawtok->str() != ELIF)) | ||
| if (ifstates.top() == AlwaysFalse || (ifstates.top() == ElseIsTrue && rawtok->str() != ELIF)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these {} do not feel super important to me. I think it's quite readable without.
this modification feels more related to uncrustify than clang-tidy, it's purely about coding style. is code updated automatically somehow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed it because it was reported in a few places only. I would not apply it to Cppcheck.
No description provided.